Skip to content

MGMT-20103: AMD_GPU operator should follor BE feature support level #2850

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

ammont82
Copy link
Member

Related to https://issues.redhat.com/browse/MGMT-20103

AMD_GPU operator should follow BE feature support level - should be disabled in case of ARM

Captura desde 2025-03-10 16-24-22

@ammont82 ammont82 requested a review from a team as a code owner March 10, 2025 15:26
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 10, 2025

@ammont82: This pull request references MGMT-20103 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.19.0" version, but no target version was set.

In response to this:

Related to https://issues.redhat.com/browse/MGMT-20103

AMD_GPU operator should follow BE feature support level - should be disabled in case of ARM

Captura desde 2025-03-10 16-24-22

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 10, 2025
@openshift-ci openshift-ci bot requested review from batzionb and ElayAharoni March 10, 2025 15:26
Copy link

openshift-ci bot commented Mar 10, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ammont82

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Mar 10, 2025
@ammont82
Copy link
Member Author

/cherry-pick releases/v2.38

@openshift-cherrypick-robot

@ammont82: once the present PR merges, I will cherry-pick it on top of releases/v2.38 in a new PR and assign it to you.

In response to this:

/cherry-pick releases/v2.38

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@rawagner
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 10, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 537c3e4 into openshift-assisted:master Mar 10, 2025
10 checks passed
@openshift-cherrypick-robot

@ammont82: new pull request created: #2851

In response to this:

/cherry-pick releases/v2.38

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants